Related to #801

Hi Paul,

This change should not be needed. Without this change, I am able to connect to the web server using the Ethernet IP address and also rtk.local.

Would you please describe the process that you are using to get the system to fail?

Thanks for your help,
Lee

Hi Lee (@LeeLeahy2 ),

I agree, it should not be needed. But unfortunately the EVK still seemed to want to default to WiFi even if Ethernet was connected.

I had been using BaseCast mode though, before going into web config. So, maybe when BaseCast starts WiFi - as it should - that then takes priority over Ethernet?

Leave it with me. I'll come up with a list of steps to replicate what I saw.

All the best,
Paul

Hi Lee (@LeeLeahy2 ),

I agree, it should not be needed. But unfortunately the EVK still seemed to want to default to WiFi even if Ethernet was connected.

I had been using BaseCast mode though, before going into web config. So, maybe when BaseCast starts WiFi - as it should - that then takes priority over Ethernet?

Leave it with me. I'll come up with a list of steps to replicate what I saw.

All the best, Paul

You are correct; didn't realize this. I also tried in normal base mode, and although the WiFi AP is started and displayed on the OLED, the ethernet interface is also running simultaneously. Given the EVK supports both, is there a reason it couldn't just display the ethernet IP address at the same time as running the access point?